Repository navigation
chore(tests): assert Firefox manifest warnings only in dedicated tests - #2696
suveshmoza wants to merge 3 commits into
Conversation
Signed-off-by: Suvesh Moza <[email protected]>
✅ Deploy Preview for creative-fairy-df92c4 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the
|
|
@suveshmoza if this is firefox extension related issue, what to do exactly? how do we test this manually? |
|
@nishu-murmu Since this change spans the The change suppresses the warning across the test suite, and we explicitly verify that the warning is handled correctly in a dedicated test case. |
|
You still didn't get what I'm trying to convey I want to manually create this scenario and implement this can you tell me how can spin up the extension (locally) for this particular scenario and able to test this warnings? |
|
Build |
|
Also the PR naming convention is not correct! Please follow the guidelines! |
@wxt-dev/analytics
@wxt-dev/auto-icons
@wxt-dev/browser
@wxt-dev/i18n
@wxt-dev/is-background
@wxt-dev/module-react
@wxt-dev/module-solid
@wxt-dev/module-svelte
@wxt-dev/module-vue
@wxt-dev/runner
@wxt-dev/storage
@wxt-dev/unocss
@wxt-dev/webextension-polyfill
wxt
commit: |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2696 +/- ##
==========================================
+ Coverage 80.32% 80.44% +0.12%
==========================================
Files 139 139
Lines 4162 4162
Branches 961 961
==========================================
+ Hits 3343 3348 +5
+ Misses 720 716 -4
+ Partials 99 98 -1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
@suveshmoza But maybe better idea is to generate those values instead of supressing it? |
|
@PatrykKuniczak Suppressing these warnings in e2e tests, as there are no related test cases. They’re better suited for unit tests, where we generate the relevant scenario and verify that the warning is logged. https://github.com/wxt-dev/wxt/pull/2696/changes#diff-c798978929d3e3cb8a7f34c9604fa1d1c83c1524b1a98fcfdd703ec0e273d147 |
Overview
Asserted Firefox missing
data_collection_permissionsandextension-idwarning in their own tests. Suppressed both warnings for the rest of the test suite, so they no longer log them. A test can still turn either warning back on.Manual Testing
Related Issue
This PR closes #2693